Fix 4.19 external oidc job failure by excluding extra and uid#75498
Conversation
|
[REHEARSALNOTIFIER]
A total of 64 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.19-amd64-nightly-gcp-upi-external-oidc-keycloak-tp-f14 |
|
@xingxingxia: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-external-oidc |
|
@xingxingxia: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse ack |
|
@xingxingxia: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: xingxingxia, xiuwang The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required |
|
@xingxingxia: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
The CI infrastructural image registry is broken, causing core-valid failing. There is on going discussion in channels. |
|
/test core-valid |
86aa9fe
into
openshift:main
4.19 job (e.g. https://url.corp.redhat.com/6893cf3 logs) fails with:
This is expected for 4.19 because the related bug fix was not intended to be backported to 4.19. Updating the script by basing on cluster version.
The pj-rehearse jobs for 4.19 and > 4.19 both passed the scripts and could go the step that runs e2e cases.